LAYER 1: EXECUTIVE CONTEXT (Cody's Notes)

LAYER 2: CORE PHILOSOPHY (The Narrative Summary)

"Not Invented Here" (NIH) is a well-documented organizational and cultural antipattern in software engineering and management. It describes the tendency of teams or organizations to avoid using or buying existing products, standards, research, or solutions of external origin, choosing instead to develop proprietary, internal alternatives.

Core Concepts

• Reinventing the Wheel: The primary manifestation of NIH is the redundant recreation of existing systems. Rather than leveraging established, community-supported, or commercial off-the-shelf solutions, teams spend limited engineering resources rebuilding common infrastructure (e.g., custom database layers, proprietary queue systems, or home-grown authentication).
• Causes of NIH Syndrome:
• Pride and Ego: The subjective belief that internal engineers can build a "better" version of a tool than the wider industry.
• Distrust of External Dependencies: A desire for total control over the codebase and fear of depending on external vendors or open-source maintainers who might deprecate libraries or introduce security vulnerabilities.
• Cultural Insularity: A corporate or team culture that prioritizes absolute autonomy over external collaboration and integration.
• Consequences of NIH:
• Opportunity Cost: Engineering hours are diverted away from core business logic (where the company must innovate to succeed) and spent on non-differentiating infrastructure.
• The Maintenance Burden: Every custom-built "wheel" requires ongoing maintenance, debugging, documentation, and onboarding—tasks that would otherwise be handled by an external community or vendor.
• Quality Deficit: Homegrown solutions rarely receive the extensive public testing, edge-case coverage, and security auditing that widely adopted third-party solutions undergo.

Connective Tissue: Lean Architecture, Site Reliability, and Product Discovery

Within the Technology Operating Model, NIH syndrome is a destructive force that directly impacts several key pillars:

• Lean Architecture and Sustainable Design (Pillar 4): Standardizing on a lean stack requires resisting the urge to build custom software for non-core capabilities. Overcoming NIH is a prerequisite for keeping architectures clean and avoiding software bloat.
• Site Reliability and Production Stability (Pillar 5): Custom-built wheels are a major source of production instability. They lack the resilience and predictability of mature external libraries. By adopting external, battle-tested solutions, engineering teams reduce their "unknown unknowns" in production.
• Developer Culture and Empowerment (Pillar 3): Combating NIH shifts developer culture from a tactical execution focus (building for building's sake) to outcome alignment. It encourages developers to be pragmatists who value solving business problems over writing proprietary code.

Generated for the Product Growth Program.

LAYER 3: FULL REFERENCE (Raw Article Content)

Source: https://en.wikipedia.org/wiki/Not_invented_here

"Not invented here" (NIH) is a term describing the tendency of social, corporate, or institutional cultures to avoid using or buying products, research, standards, or knowledge from external sources. It is generally used in a pejorative sense.

Overview

The reasons for this behavior are diverse, ranging from a genuine desire to support local economies or avoid patent infringement, to more negative drivers such as jealousy, tribalism, fear of the unknown, or an unwillingness to acknowledge the work of others.

It is considered an "anti-pattern" in business and software development because it can slow down innovation and lead to redundant work. Research, such as the 1982 study by Ralph Katz and Thomas J. Allen, indicates that teams exhibiting NIH tendencies often experience a decline in performance over time as they become increasingly isolated from external information sources.

In Programming

In software development, NIH is often discussed as a perceived bias where developers or teams prefer to write their own code or build custom frameworks rather than using established third-party libraries, open-source projects, or existing tools.

• The "Individualist" Myth: It is often jokingly or critically remarked in management circles that programmers are "individualists" who would rather redo everything themselves. However, many practitioners argue that this is a misunderstanding; developers are generally pragmatic and will reuse high-quality, well-documented code if it is truly accessible and solves their specific problem efficiently.
• Rational Reasons for "NIH": What is labeled as "Not Invented Here" is sometimes a deliberate strategy to maintain control over a product's destiny. For instance, a company might avoid external dependencies to ensure long-term stability, avoid licensing issues, or tailor a component precisely to their unique architecture where a generic solution would fall short.
• Corporate Dynamics: Large companies with established ecosystems (e.g., Microsoft, Oracle, Facebook) often face accusations of NIH syndrome because they prioritize their own proprietary technologies (like C#, Java, or internal frameworks) over adopting competing external platforms.

In Business

In the broader business world, NIH syndrome acts as a barrier to innovation, collaboration, and efficiency.

• Management vs. Engineering: In business settings, NIH often manifests as a top-down refusal to adopt market-leading solutions, leading to wasted resources as internal teams struggle to "reinvent the wheel."
• Market Share and Control: Businesses sometimes adopt this stance to maximize their market share by keeping customers locked into their own proprietary ecosystem. By creating a closed environment, companies believe they can control the "common denominator" of user needs without relying on third-party vendors.
• Risks: The primary risk of NIH syndrome in business is the high cost of maintenance and the potential for a product to fall behind the industry standard. When a company invests heavily in its own proprietary tools that are not industry-standard, it can become difficult to attract talent, integrate with other systems, or keep pace with faster-moving competitors.

Counter-Mindsets

Terms for the opposite mindset include "proudly found elsewhere" (PFE), "invented elsewhere," or sometimes "invented here."

Generated for the Product Growth Program.